This page last changed on Jan 09, 2009 by aunger.

Class lists

No longer valid

The info in this page is no longer accurate, and shouldn't be used as a guide until it is updated.

When running the DIY with Overlays turned on, the DIY will optionally include the OTClassListManager bundle in the overlay. Whether it is included or not is determined by whether the group_list_url parameter is included in the request. The group_list_url parameter should be a full url pointing to a location where an otml snippet is located or generated. The otml should be basic and contain one object: an OTObjectSet which encapsulates an OTObjectList of OTUserObject objects (and their possible parameters).

Example:

<?xml version="1.0" encoding="UTF-8"?>
<otrunk id="a341a1a2-dd32-102b-a487-005056801240">
    <imports>
        <import class="org.concord.framework.otrunk.wrapper.OTObjectSet"/>
        <import class="org.concord.otrunk.user.OTUserObject"/>
    </imports>
    <objects>
        <OTObjectSet>
            <objects>
                <OTUserObject name="Aaron Student">
                    <userDataMap>
                        <entry key="portal_member_id">
                            <string>2090</string>
                        </entry>
                        <entry key="diy_member_id">
                            <string>2055</string>
                        </entry>
                        <entry key="sds_member_id">
                            <string>5934</string>
                        </entry>
                        <entry key="cc_member_id">
                            <string>36410</string>
                        </entry>
                    </userDataMap>
                </OTUserObject>
                <OTUserObject name="Aunger Student">
                    <userDataMap>
                        <entry key="portal_member_id">
                            <string>7343</string>
                        </entry>
                        <entry key="diy_member_id">
                            <string>1263</string>
                        </entry>
                        <entry key="sds_member_id">
                            <string>26888</string>
                        </entry>
                        <entry key="cc_member_id">
                            <string>42305</string>
                        </entry>
                    </userDataMap>
                </OTUserObject>
                <OTUserObject name="Aunger Student2">
                    <userDataMap>
                        <entry key="portal_member_id">
                            <string>7344</string>
                        </entry>
                        <entry key="diy_member_id">
                            <string>1264</string>
                        </entry>
                        <entry key="sds_member_id">
                            <string>26889</string>
                        </entry>
                        <entry key="cc_member_id">
                            <string>42306</string>
                        </entry>
                    </userDataMap>
                </OTUserObject>
                <OTUserObject name="Aunger Student3">
                    <userDataMap>
                        <entry key="portal_member_id">
                            <string>7345</string>
                        </entry>
                        <entry key="diy_member_id">
                            <string>1265</string>
                        </entry>
                        <entry key="sds_member_id">
                            <string>26890</string>
                        </entry>
                        <entry key="cc_member_id">
                            <string>42307</string>
                        </entry>
                    </userDataMap>
                </OTUserObject>
            </objects>
        </OTObjectSet>
    </objects>
</otrunk>

Inside the activity, you can ask for the OTClassListManager bundle, and call getUserList() to get the OTObjectList of OTUserObjects. You can then do as you wish with that list of users.

This is useful for providing an up-to-date, dynamic list of users in a class which can then be used for things like selecting workgroup partners, personalizing activities for the class, generating random pairings for discussion steps, etc.

Document generated by Confluence on Jan 27, 2014 16:52